Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed the user management page cypress issue #9384

Merged
merged 2 commits into from
Dec 11, 2024
Merged

Conversation

nihal467
Copy link
Member

@nihal467 nihal467 commented Dec 11, 2024

Proposed Changes

  • Fixes #issue_number
  • Change 1
  • Change 2
  • More?

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

  • Add specs that demonstrate bug / test a new feature.
  • Update product documentation.
  • Ensure that UI text is kept in I18n files.
  • Prep screenshot or demo video for changelog entry, and attach it to issue.
  • Request for Peer Reviews
  • Completion of QA

Summary by CodeRabbit

  • New Features

    • Added a test case to verify working hours in user profiles.
    • Introduced a scenario for linking and unlinking facilities for multiple users, ensuring visibility in user cards.
  • Bug Fixes

    • Enhanced verification process for user details and linked facilities with additional assertions.
  • Refactor

    • Updated the method for verifying working hours to check for content presence instead of input field interaction.

@nihal467 nihal467 requested a review from a team as a code owner December 11, 2024 15:14
Copy link
Contributor

coderabbitai bot commented Dec 11, 2024

Walkthrough

The changes in this pull request enhance the Cypress end-to-end test suite for user management. A new test case verifies the reflection of working hours in user profiles, including navigation to the profile after submitting hours. Additionally, a scenario for linking and unlinking facilities for multiple users is introduced, ensuring correct visibility in user cards. The verifyWorkingHours and verifyProfileWorkingHours methods in the ManageUserPage class are updated to check for content presence instead of input field interaction. Overall, the modifications expand test coverage while maintaining the existing structure.

Changes

File Path Change Summary
cypress/e2e/users_spec/UsersManage.cy.ts Added tests for verifying working hours in user profiles and linking/unlinking facilities for multiple users.
cypress/pageobject/Users/ManageUserPage.ts Updated verifyWorkingHours and verifyProfileWorkingHours methods to check content presence instead of input field visibility.

Possibly related PRs

Suggested labels

needs review, tested

Suggested reviewers

  • rithviknishad

Poem

🐇 In the land of tests where rabbits play,
New cases hop in, brightening the day.
Working hours checked, and links made right,
User cards gleam, a wonderful sight!
With every assertion, our code takes flight,
Testing together, we’ll conquer the night! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 40ea811 and 1160d6e.

📒 Files selected for processing (1)
  • cypress/pageobject/Users/ManageUserPage.ts (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • cypress/pageobject/Users/ManageUserPage.ts

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Dec 11, 2024

Deploy Preview for care-ohc ready!

Name Link
🔨 Latest commit 1160d6e
🔍 Latest deploy log https://app.netlify.com/sites/care-ohc/deploys/6759b2a8b6002a0008e5cdee
😎 Deploy Preview https://deploy-preview-9384--care-ohc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

cloudflare-workers-and-pages bot commented Dec 11, 2024

Deploying care-fe with  Cloudflare Pages  Cloudflare Pages

Latest commit: 1160d6e
Status: ✅  Deploy successful!
Preview URL: https://c4827baf.care-fe.pages.dev
Branch Preview URL: https://flaky-test.care-fe.pages.dev

View logs

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)
cypress/pageobject/Users/ManageUserPage.ts (1)

196-198: Consider consolidating working hours verification methods

While the implementation using cy.verifyContentPresence is good, having two similar methods (verifyWorkingHours and verifyProfileWorkingHours) with different implementations could lead to maintenance issues.

Consider consolidating both methods to use the same verification approach:

  verifyWorkingHours(expectedHours: string) {
    cy.verifyContentPresence("#view-average_weekly_working_hours", [
      expectedHours,
    ] as string[]);
  }

-  verifyProfileWorkingHours(expectedHours: string) {
-    cy.get("#view-average_weekly_working_hours").should(
-      "contain.text",
-      expectedHours,
-    );
-  }
+  verifyProfileWorkingHours(expectedHours: string) {
+    this.verifyWorkingHours(expectedHours);
+  }
cypress/e2e/users_spec/UsersManage.cy.ts (1)

308-308: Enhance test coverage for working hours verification

While verifying working hours across different views is good, consider adding negative test cases to ensure robust validation.

Add test cases for:

  • Non-numeric values
  • Negative values
  • Empty values
  • Decimal values

Example:

// Add these test cases before setting the valid working hours
const invalidInputs = ['abc', '-1', '', '23.5'];
for (const input of invalidInputs) {
  manageUserPage.clearProfessionalInfo();
  manageUserPage.typeInWeeklyWorkingHours(input);
  manageUserPage.clickSubmit();
  manageUserPage.verifyErrorText("Average weekly working hours must be a number between 0 and 168");
}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 113dddd and 40ea811.

📒 Files selected for processing (2)
  • cypress/e2e/users_spec/UsersManage.cy.ts (1 hunks)
  • cypress/pageobject/Users/ManageUserPage.ts (1 hunks)

Copy link

cypress bot commented Dec 11, 2024

CARE    Run #4010

Run Properties:  status check passed Passed #4010  •  git commit 1160d6e543: Fixed the user management page cypress issue
Project CARE
Branch Review flaky-test
Run status status check passed Passed #4010
Run duration 05m 26s
Commit git commit 1160d6e543: Fixed the user management page cypress issue
Committer Mohammed Nihal
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 153
View all changes introduced in this branch ↗︎

@nihal467 nihal467 self-assigned this Dec 11, 2024
@rithviknishad rithviknishad merged commit 3ba5dc6 into develop Dec 11, 2024
58 checks passed
@rithviknishad rithviknishad deleted the flaky-test branch December 11, 2024 15:55
Copy link

@nihal467 Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants